Rack controller with native support for intelligent patching equipment installed in multiple racks

ABSTRACT

One embodiment is directed to a multi-rack rack controller for an automated infrastructure management (AIM) system comprising a plurality of independent patching equipment bus interfaces. Another embodiment is directed to a rack controller comprising at least one rack controller interface configured to connect the rack controller to another rack controller. Each rack controller interface comprises a respective termination circuit. The rack controller is configured to determine whether each rack controller interface is connected to another rack controller as a function of a respective sense signal developed by the termination circuit associated with said rack controller interface. Another embodiment is directed to a rack controller comprising a base unit having a locate button disposed on the front of the base unit. Other embodiments are disclosed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a national stage application, filed under 35 U.S.C.Section 371, of International Patent Application No. PCT/US2018/036137,filed on Jun. 5, 2018, which claims the benefit of United StatesProvisional Patent Application Serial No. 62/515,496, filed Jun. 5, 2017and titled “RACK CONTROLLER WITH NATIVE SUPPORT FOR INTELLIGENT PATCHINGEQUIPMENT INSTALLED IN MULTIPLE RACKS”, the contents of all of which areincorporated herein by reference in their entireties.

BACKGROUND

Automated Infrastructure Management (AIM) systems are used to trackconnections that are made between ports (or other connection points)that exist in the information technology (IT) infrastructure of a datacenter. AIM systems are typically designed to work with patchingequipment that has AIM-related functionality for tracking connectionsmade at the ports of such patching equipment. Such “intelligent”patching equipment is typically mounted in racks. Each rack typicallyincludes a rack controller that is communicatively coupled to theAIM-related functionality for each item of intelligent patchingequipment mounted in that rack. The rack controller aggregatesconnection information for the ports of the patching equipment in theassociated rack. Each rack controller also typically includes, or iscoupled to, a display device for displaying information for a userlocated at the rack and a user-input device for receiving user-inputfrom the user. In one example, the display device and the user-inputdevice are implemented together in a liquid crystal display (LCD) with atouch screen that is used for both displaying information and receivinguser input. This combination of a display device and user-input deviceis also referred to here as a “display unit.”

The display unit is used by the rack controller to a display a userinterface for software that executes on the associated rack controller.This rack controller software is used, for example, to displayinformation for a user about connections made at the ports of patchingequipment installed in the associated rack and to receive informationfrom a user about connections made at the ports of such patchingequipment. Such rack controller software, and the AIM system moregenerally, is typically designed to require the use of a display unit atthe rack controller.

Typically, with such AIM systems, each rack controller is designed to beconnected to only the patching equipment that is installed in the samerack in which the rack controller is installed. A single bus (alsoreferred to here as a “patching equipment bus”) is typically used tocouple the rack controller to the intelligent patching equipmentinstalled in the same rack.

US Patent Publication No. 20100141379 describes the use of “patchingequipment bus extenders” that can be used in situations where a rackcontroller is installed in a first rack, and patching equipment busextenders are mounted on adjacent racks so that intelligent patchingequipment installed in those adjacent racks can be connected to the rackcontroller installed in the first rack. The patching equipment busextenders are used to connect the patching equipment installed in theadjacent racks to the same bus used to connect the patching equipmentinstalled in the first rack to the rack controller. However, as notedabove, such rack controllers are typically designed to work withpatching equipment installed in the same rack that the rack controlleris installed in. That is, such “single-rack” rack controllers typicallydo not have the capacity to be connected to more than the number ofitems of patching equipment that would typically be installed in asingle rack, even if patching equipment bus extenders are used toconnect the rack controller to patching equipment installed in adjacentracks. In other words, patching equipment bus extenders are typicallyonly useful in situations where the first rack in which the rackcontroller is installed is not fully populated with patching equipment,and there is only a small number of items of patching equipmentinstalled in the adjacent racks.

Also, the software executing on such a single-rack rack controller isconfigured to assume that all intelligent patching equipment coupled tothe patching equipment bus is installed in the same rack that the rackcontroller is installed in. That is, such rack controller software doesnot typically include functionality for dealing with patching equipmentthat is not located in the same rack as the rack controller.

For the purposes of an AIM system, multiple racks may be assigned to a“zone,” where the respective rack controllers for each of the racks in azone are connected together in a daisy chain with one rack controller(the head of the daisy chain) having an external connection to anETHERNET local area network (LAN) and, ultimately, the AIM systemmanager.

To support the daisy chaining of rack controllers, each rack controllercan include two RJ-45 jacks, one of which is connected to either anupstream rack controller or the external ETHERNET LAN and the other ofwhich either is connected to a downstream rack controller, is connectedto the external ETHERNET LAN, or is not connected to anything.Typically, the rack controller includes a respective manual switch foreach such RJ-45 jack to indicate how the respective RJ-45 is configured(that is, in the case of the first RJ-45 jack, whether the first RJ-45jack is connected to either an upstream rack controller or the ETHERNETLAN, or, in the case of the second RJ-45 jack, whether the second RJ-45jack is either connected to a downstream rack controller, is connectedto the external ETHERNET LAN, or is not connected to anything).

SUMMARY

One embodiment is directed to a multi-rack rack controller for use in anautomated infrastructure management (AIM) system. The rack controllercomprises a processor configured to execute software and a plurality ofindependent patching equipment bus interfaces. Each bus interface isconfigured to couple the processor to a respective patching equipmentbus assembly installed in a respective one of multiple racks in whichintelligent patching equipment is installed for communicating with andproviding power to the intelligent patching equipment.

Another embodiment is directed to a rack controller for use in anautomated infrastructure management (AIM) system. The rack controllercomprises a processor configured to execute software and at least onepatching equipment bus interface. Each patching equipment bus interfaceis configured to couple the processor to a respective patching equipmentbus assembly installed in a respective rack in which intelligentpatching equipment is installed for communicating with and providingpower to the intelligent patching equipment. The rack controller furthercomprises at least one rack controller interface, each rack controllerinterface configured to connect the rack controller to another rackcontroller. Each rack controller interface comprises a respectivetermination circuit that is configured to develop a respective firstpredetermined level for a respective sense signal of said rackcontroller interface when said rack controller interface is connected toanother rack controller and develop a respective second predeterminedlevel for the respective sense signal of said rack controller interfacewhen said rack controller interface is not connected to another rackcontroller. The processor is configured to determine whether each rackcontroller interface is connected to another rack controller as afunction of the respective sense signal.

Another embodiment is directed to a rack controller for use in anautomated infrastructure management (AIM) system. The rack controllercomprises a base unit comprising a processor configured to executesoftware and at least one patching equipment bus interface. Eachpatching equipment bus interface is configured to couple the processorto a respective patching equipment bus assembly installed in arespective rack in which intelligent patching equipment is installed forcommunicating with and providing power to the intelligent patchingequipment. The rack controller further comprises a locate buttondisposed on the front of the base unit, the locate button coupled to theprocessor. The locate button can be actuated in order to provide a userinput to the processor even if there is not a display unit coupled tothe base unit and to cause the rack controller to send a messageoperable to cause an app executing on a portable device to showinformation associated with at least one of the rack controller, therack, or the patching equipment installed in the rack.

Other embodiments are disclosed.

The details of various embodiments are set forth in the accompanyingdrawings and the description below. Other features and advantages willbecome apparent from the description, the drawings, and the claims.

DRAWINGS

FIG. 1 illustrates one exemplary embodiment of an automatedinfrastructure management (AIM) system that is configured to trackconnections that are made using items of patching equipment.

FIG. 2 is a block diagram illustrating one exemplary embodiment of amulti-rack rack controller.

FIG. 3 is a block diagram illustrating one example of the daisy chainingof rack controllers to form a rack manager (RM) LAN.

FIG. 3 is a flow diagram of one exemplary embodiment of a method ofmuting a repeater system.

FIG. 4 is a block diagram illustrating exemplary embodiments of thetermination circuits shown in FIG. 2 .

FIG. 5 illustrates an exemplary embodiment of an automatedinfrastructure management (AIM) system that is configured to trackconnections that are made using items of patching equipment thatimplement different types of AIM functionality.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

FIG. 1 illustrates one exemplary embodiment of an automatedinfrastructure management (AIM) system 100 that is configured to trackconnections that are made using items of patching equipment 104. Theconnections can be made with various types of cabling, including,without limitation, copper cables and fiber optic cables.

The system 100 shown in FIG. 1 can be implemented in a data center orenterprise application. Other embodiments can be implemented in otherways (for example, where the system 100 is implemented in a centraloffice or other facility of a telecommunication service provider and/orin another part of the telecommunication service provider's network).

The patching equipment 104 is deployed in racks 106 along with otheritems of equipment (not shown) (such as servers, routers, and switches).

In one aspect illustrated in FIG. 1 , the AIM system 100 is configuredto work with patching equipment 104 (such as patch panels) that has AIMfunctionality 110 for tracking connections at the ports 112 of thepatching equipment 104. This patching equipment 104 is also referred tohere as “intelligent patching equipment” 104. In one aspect, the AIMfunctionality 110 comprises, for each port 112 of the associated item ofpatching equipment 104, a sensor, reader, interface, or other circuitry(collectively referred to here as a “sensor”) 114 for use in determiningthe presence of, and/or information from or about, a connector and/orcable attached to the associated port 112. In one aspect, the AIMfunctionality 110 comprises, for each port 112 of the associated item ofintelligent patching equipment 104, one or more visual indicators 116(such as one or more light emitting diodes (LEDs)) for providing avisual indication to a user, for example, to enable the user to visuallyidentify that particular port 112. In one aspect, the AIM functionality110 also comprises, for each port 112 of the associated item ofintelligent patching equipment 104, a respective user-input device 118(such as a button) by which a user is able to select that port 112.

Various types of AIM technology can be used. One type of AIM technologyinfers connection information by sensing when connectors are inserted orremoved from ports of the various devices. Another type of AIMtechnology makes use of so-called “ninth wire” or “tenth wire”technology. Ninth wire/tenth wire technology makes use of special cablesthat include one or more extra conductors or signal paths that are usedfor determining which port each end of the cable is inserted into. Yetanother type of AIM technology makes use of an Electrically ErasableProgrammable Read-Only Memory (EEPROM) or other storage device that isintegrated with or attached to a connector on a cable. The storagedevice is used to store an identifier for the cable or connector alongwith other information. The port (or other connector) into which theassociated connector is inserted is configured to read the informationstored in the EEPROM when the connector is inserted into the port ofpatch panel or other item of patching equipment. A similar approach canbe used with optical machine-readable representations of data (such asbarcodes or QR codes).

Another type of AIM technology makes use of radio frequencyidentification (RFID) tags and readers. With RFID technology, an RFIDtag is attached to or integrated with a connector on a cable. The RFIDtag is used to store an identifier for the cable or connector along withother information. The RFID tag is typically then read using an RFIDreader after the associated connector is inserted into a port (or otherconnector) of a patch panel or other item of patching equipment.

Other types of AIM technology can be used.

In one aspect illustrated in FIG. 1 , each item of intelligent patchingequipment 104 includes a respective programmable processor 120 that iscommunicatively coupled to the other AIM functionality 110 in that itemof patching equipment 104. The programmable processor 120 is configuredto execute software that reads or otherwise receives information fromeach sensor 114, controls the state of each visual indicator 116, anddetermines the state of each button 118.

The sensor 114, visual indicator 116, button 118, and processor 120 canbe natively integrated into the patching equipment 104 or can bepackaged into a retrofit kit that can be installed on already deployedpatching equipment 104.

The AIM system 100 further comprises one or more rack controllers 122.

Each rack controller 122 is configured to be connected to, and manage,patching equipment 104 having AIM functionality 110 that is installed inmultiple racks 106. That is, each such rack controller 122 is a“multi-rack” rack controller 122.

In this exemplary embodiment, each multi-rack rack controller 122 isconfigured to be connected to patching equipment 104 that is installedin three racks 106, though it is to be understood that this is merelyone example and that, in other embodiments, one or more multi-rack rackcontrollers 122 can be configured to be connected to patching equipment104 installed in a different number of racks 106.

In this exemplary embodiment, each multi-rack rack controller 122 isconfigured to use three, separate and independent patching equipmentbuses 123 to communicate with intelligent patching equipment 104installed in the three racks 106.

Each rack controller 122 aggregates connection information for the ports112 of the patching equipment 104 in the associated racks 106. Morespecifically, each rack controller 122 is configured to use the sensor114 associated with each port 112 of the patching equipment 104 mountedin the associated rack 106 to monitor the state of each port 112 andidentify connection or disconnection events occurring at that port 112.Also, each rack controller 122 is configured to illuminate or otherwiseactuate any visual indicators 116 associated with the port 112 and tomonitor the state of each button 118 associated with that port 112 andidentify any events occurring at such buttons 118 (for example, buttonpress and/or release events).

One exemplary embodiment of a multi-rack rack controller 122 is shown inFIG. 2 . In one aspect illustrated in FIG. 2 , each rack controller 122comprises at least one programmable processor 124 on which software orfirmware 126 executes. The software 126 comprises program instructionsthat are stored (or otherwise embodied) on an appropriate non-transitorystorage medium or media 128 from which at least a portion of the programinstructions are read by the programmable processor 124 for executionthereby. The software 126 is configured to cause the processor 124 tocarry out at least some of the operations described here as beingperformed by that rack controller 122. Although the storage medium 128is shown in FIG. 2 as being included in the controller 122, it is to beunderstood that remote storage media (for example, storage media that isaccessible over a network) and/or removable media can also be used. Inone aspect illustrated in FIG. 2 , each rack controller 122 alsocomprises memory 130 for storing the program instructions and anyrelated data during execution of the software 126.

Each multi-rack rack controller 122 also includes a display device 132for displaying information for a user located at the associated rack 106and a user-input device 134 for receiving user-input from such a user.In one aspect illustrated in FIGS. 1 and 2 , the display device 132 andthe user-input device 134 are implemented together in a liquid crystaldisplay (LCD) touch screen that is used for both displaying informationand receiving user input. This combination of a display device 132 anduser-input device 134 is also referred to here as a “display unit” 136.In this example embodiment, the multi-rack controller 122 is configuredso that the display unit 136 can be moved relative to the rest of themulti-rack rack controller 122 (for example, the display unit 136 can bemoved in and out, moved up and down, tilted, rotated, etc.). Tofacilitate this, the rest of the rack controller 122 is implemented in abase unit 138, where the display unit 136 is coupled to the base unit138 for power, ground, and communications using, for example, a cable(for example a USB cable and USB interfaces 182 and 184). In this way,the display unit 136 can be moved relative to the base unit 138 toenable a user to more easily view and/or touch the display unit 136.

Each multi-rack controller 122 includes a power supply 140 that isconfigured to provide power for the base unit 136, the display unit 138,and the patching equipment 104 connected to the multi-rack rackcontroller 122. In this example, the power supply 140 includes two powerconnectors 142 so that two external power adapters (not shown) can beused to couple the power supply 140 in the rack controller 122 to twoalternating current (AC) power sources. Two power connectors 142, poweradapters, and power sources are used for power redundancy. Also, thepower supply 140 and power adapters are configured and designed to havesufficient capacity to supply power to racks 106 that are fullypopulated with intelligent patching equipment 104.

As shown in FIG. 1 , in this exemplary embodiment, each of the patchingequipment buses 123 is implemented using a respective patching equipmentbus assembly 146 that is mounted to one of the rails of thecorresponding rack 106. The patching equipment bus assembly 146comprises multiple patching equipment bus connectors 148 that areelectrically coupled to one another via the bus 124. The patchingequipment bus assembly 146 also comprises a housing 150 that enclosesthe conductors (or other circuitry or inter-connects) that implement thebus 123 and that supports the bus connectors 148. The housing 150 isconfigured to be mounted to one of the rails of the rack 106 (forexample, via an adhesive, one or more fasteners, or the like).

As noted above, in this exemplary embodiment, each multi-rack rackcontroller 122 is configured to use three, separate and independentpatching equipment buses 123 to communicate with intelligent patchingequipment 104 installed in three racks 106. To do this, each multi-rackrack controller 122 includes three patching equipment bus interfaces 152to connect the rack controller 122 to the three patching equipment buses123 and to provide power and ground to the patching equipment 104installed in that rack 106 via the patching equipment bus 123 and toenable communications between the processor 124 in the rack controller122 and the patching equipment 104 installed in the rack 106 via thepatching equipment bus 123. Each patching equipment bus interface 152comprises a respective patching equipment bus connector 154 (shown inFIG. 2 ) that can be used with an appropriate cable to connect thatpatching equipment bus connector 154 to a patching equipment busconnector 148 of a respective patching equipment bus assembly 146.

In this exemplary embodiment, each patching equipment bus 123 comprisesa twenty-line bus, and, accordingly, each of the patching equipment busconnectors 148 and 154 comprises a twenty-pin connector. Sixteen of thetwenty lines of each patching equipment bus 123 are used for an I2C busto provide power, ground, and communications to the patching equipment104. The other four lines of each patching equipment bus 123 are used toimplement two RS-485 serial buses for programming and debuggingpurposes. However, it is to be understood, that this one example andthat other embodiments can be implemented in other ways.

By using multiple, separate and independent patching equipment businterfaces 152 along with a sufficiently powerful processor 124 andpower supply 140, the multi-rack rack controller 122 is able to supportmore than a single rack's worth of patching equipment 104 in themultiple racks 106. This is in contrast to the approach described abovein the Background that uses the patching equipment bus extendersdescribed in US Patent Publication No. 20100141379 and a single-rackrack controller that typically only supports a single rack's worth ofintelligent patching equipment.

The patching equipment bus connectors 154 of the multi-rack rackcontroller 122 can be connected to the patching equipment bus assemblies146 installed in the various racks 106 in accordance with apredetermined scheme or policy. As a result, the software 126 executingon the processor 124 of the multi-rack rack controller 122 can use thispredetermined scheme or policy to determine, for a given item ofpatching equipment 104 that the controller 122 is communicating with,which rack 106 that item is installed in.

In the exemplary embodiment shown in FIGS. 1 and 2 , the multi-rack rackcontroller 122 includes three patching equipment bus connectors 154 thatare arranged in row. A predetermined policy can be used that specifiesthat the multi-rack rack controller 122 be installed in the center rack106. This policy can also specify that the patching equipment busconnector 154 on the left side of the row be used to connect thecontroller 122 to the patching equipment bus assembly 146 mounted in theleftmost rack 106, that the patching equipment bus connector 154 in thecenter of the row be used to connect the controller 122 to the patchingequipment bus assembly 146 mounted in the center rack 106 (which is therack 106 in which the rack controller 122 is installed), and that thepatching equipment bus connector 154 on the right side of the row beused to connect the controller 122 to the patching equipment busassembly 146 mounted in the rightmost rack 106.

Then, the software 126 executing on the processor 124 in the multi-rackrack controller 122 is able to determine, for a given item of patchingequipment 104 that the controller 122 is communicating with, which rack106 that item of patching equipment 104 is installed in by identifyingwhich patching equipment bus interface 152 is being used to communicatewith that item of patching equipment 104. This is in contrast to theapproach described above in the Background that uses the patchingequipment bus extenders described in US Patent Publication No.20100141379, where the single-rack rack controller is not able toautomatically determine which rack an item of patching equipment isinstalled in and instead assumes all items of patching equipment areinstalled in the same rack.

In the exemplary embodiment shown in FIG. 1 , for the purposes of theAIM system 100, multiple racks 106 may be assigned to a zone 158, wherethe multi-rack rack controllers 122 for the racks 106 in a zone 158 areconnected together in a daisy chain with one controller 122 (the head ofthe daisy chain) having an external connection to an external network160 via which the controllers 122 are able to ultimately communicatewith an AIM system manager 162. In this example, the external network160 is implemented as an ETHERNET local area network (LAN), which isalso referred to as the “customer LAN.”

In this embodiment, each multi-rack rack controller 122 comprises anexternal network interface 164 that can be used to directly connect thatmulti-rack rack controller 122 to the external network 160. As notedabove, in this exemplary embodiment, the external network 160 isimplemented as an ETHERNET LAN and, as a result, the external networkinterface 164 comprises an ETHERNET interface and is also referred tohere as “ETHERNET interface” 164 or “customer LAN interface” 164.

The various rack controllers 122 provide asset and connectioninformation to the AIM system manager 162. In one aspect, the AIM systemmanager 162 is configured to compile asset and connection informationacross all of the zones 158 and to provide an end-to-end trace of theconnections made across those zones 158. The AIM system manager 162stores the asset and connection information for the various zones 158 inan AIM database 166.

In this embodiment, each multi-rack rack controller 122 also comprisestwo rack controller interfaces 168 that can be used to connect each rackcontroller 122 to the other multi-rack rack controllers 122 in its zone158 in a daisy-chain configuration. The rack controllers 122 for a givenzone 158 that are daisy chained together form a rack controller (or rackmanager) network, which is also referred to as a “rack manager LAN” or“RM LAN” and, as a result, the rack controller interfaces 168 are alsoreferred to here as “RM LAN interfaces” 168.

In this example (as shown in FIG. 2 ), a first one of the RM LANinterfaces 168 is designated the “IN” RM LAN interface 168, while theother RM LAN interface 168 is designated the “OUT” RM LAN interface 168.The IN RM LAN interface 168 is used for connecting the associated rackcontroller 122 to either an upstream rack controller 122 in the RM LANor to no rack controller 122. The OUT RM LAN interface 168 is used forconnecting the associated rack controller 122 to either a downstreamupstream rack controller 122 in the RM LAN or to no rack controller 122.One example of the daisy chaining of rack controllers 122 to form a RMLAN is shown in FIG. 3 .

In this example, the RM LAN is implemented using 10/100BASE-T ETHERNETcabling terminated with RJ-45 plugs, and each RM LAN interface 168comprises a respective RJ-45 jack 170 configured to be connected to aRJ-45 plug attached to an 10/100BASE-T ETHERNET cable. In this example,ETHERNET traffic communicated to and from the customer LAN 160 isforwarded as needed among the rack controllers 122 over the RM LAN.Also, in this example, one of the unused pairs in the 10/100BASE-TETHERNET cabling is also used to implement a RS-485 bus over the RM LAN.

Each rack controller 122 (more specifically, the software 126 executingon the processor 124 in the controller 122) is configured toautomatically determine the connectivity status of its RM LAN interfaces168 and communicate over the RM LAN and customer LAN 160 accordingly.The IN and OUT RM LAN interface 168 comprises respective terminationdetermination circuits 172 and 174. Each termination circuit 172 and 174is configured to develop a signal that can be detected by the rackcontroller 122 to determine the connectivity status of its associated RMLAN interfaces 168.

FIG. 4 is a block diagram illustrating exemplary embodiments of thetermination circuits 172 and 174 shown in FIG. 2 . Termination circuit172 is implemented as a part of the IN RM LAN interface 168, andtermination circuit 174 is implemented as a part of the OUT RM LANinterface 168.

In this example, ETHERNET traffic is communicated over the 10/100BASE-TETHERNET cabling in the standard way using the standard pairs (that is,using pair 2 (corresponding to pins 3 and 6) and pair 3 (correspondingto pins 1 and 2)). Also, one of the pairs in the 10/100BASE-T ETHERNETcabling not used for ETHERNET traffic is used for the RS-485 bus (inthis example, pair 1 (corresponding to pins 4 and 5)), and another oneof the pairs in the 10/100BASE-T ETHERNET cabling not used for ETHERNETtraffic is used for developing a signal that can be detected by the rackcontroller 122 to determine the connectivity status of its associated RMLAN interfaces 168 (in this example, pair 4 (corresponding to pins 7 and8)).

In this example, a signal (485_TERM_SENSE) is developed on pin 7 of theRJ-45 connector 170 of the IN RM LAN interface 168. The terminationcircuit 172 comprises a first resistor (R1) 402 that is coupled inseries between a positive supply voltage rail (+ISO_V) and pin 7 of theRJ-45 connector 170 for the IN RM LAN interface 168. Pin 8 of the RJ-45connector 170 of the IN RM LAN interface 168 is coupled to ground(ISO_GND). In this example, the first resistor R1 is implemented using a10 kiloohm resistor.

In this example, a signal (485_TERM_SENSE) is developed on pin 7 of theRJ-45 connector 170 of the OUT RM LAN interface 168. The terminationcircuit 174 comprises a second resistor (R2) 404 and a third resistor(R3) 406 coupled in series between the positive supply voltage rail+ISO_V and ground ISO_GND. Pin 7 of the RJ-45 connector 170 of the OUTRM LAN interface 168 is coupled via a fourth resistor (R4) 408 to thejunction between the second and third resistors R2 and R3. In thisexample, the second and fourth resistors R2 and R4 are implemented using10 kiloohm resistors, and the third resistor R3 is implemented using a4.5 kiloohm resistor.

When two rack controllers 122 are daisy chained together, the OUT RM LANinterface 168 of a first (upstream) rack controller 122 is connected tothe IN RM LAN interface 168 of a second (downstream) rack controller 122via a 10/100BASE-T ETHERNET cable. When this occurs, the terminationscircuits 172 and 174 of the OUT and IN RM LAN interfaces 168 of thefirst and second rack controllers 122, respectively, are coupled to eachother and the 485_TERM_SENSE signal on pin 7 of the RJ-45 connectors 170of the OUT and IN RM LAN interfaces 168 will have a first predeterminedlevel (3.27 Volts in this example).

When no 10/100BASE-T ETHERNET cable is connected to the OUT RM LANinterface 122 of a rack controller 122, the 485_TERM_SENSE signal on pin7 of the RJ-45 connector 170 of the OUT RM LAN interface 168 will have asecond predetermined level (1.55 Volts in this example).

When no 10/100BASE-T ETHERNET cable is connected to the IN RM LANinterface 122 of a rack controller 122, the 485_TERM_SENSE signal on pin7 of the RJ-45 connector 170 of the IN RM LAN interface 168 will have athird predetermined level (5 Volts in this example).

By checking the level of the signal on the 485_TERM_SENSE signal on pin7 of the RJ-45 connectors 170 of the IN and OUT RM LAN interfaces 168,the software 126 executing on the processor 124 in a rack controller 122is able to determine the connectivity status of its associated RM LANinterfaces 168.

In this example, when the software 126 executing on the processor 124 ina rack controller 122 detects the first predetermined level for the485_TERMS_SENSE signal on pin 7 of the RJ-45 connector 170 of the IN RMLAN interface 168, the software 126 concludes that the IN RM LANinterface 168 is connected to the OUT RM LAN interface 168 of anotherrack controller 122. Likewise, in this example, when the software 126executing on the processor 124 in a rack controller 122 detects thefirst predetermined level for the 485_TERMS_SENSE signal on pin 7 of theRJ-45 connector 170 of the OUT RM LAN interface 168, the software 126concludes that the OUT RM LAN interface 168 is connected to the IN RMLAN interface 168 of another rack controller 122.

In this example, when the software 126 executing on the processor 124 ina rack controller 122 detects the second predetermined level for the485_TERMS_SENSE signal on pin 7 of the RJ-45 connector 170 of the OUT RMLAN interface 168, the software 126 concludes that the OUT RM LANinterface 168 is not connected to another rack controller 122. In thisexample, when the software 126 executing on the processor 124 in a rackcontroller 122 detects the third predetermined level for the485_TERMS_SENSE signal on pin 7 of the RJ-45 connector 170 of the IN RMLAN interface 168, the software 126 concludes that the IN RM LANinterface 168 is not connected to another rack controller 122. In thisway, the software 126 is able to determine the connectivity status ofits associated RM LAN interfaces 168. This approach does not make use ofmanual switches, which simplifies the process of installing such rackcontrollers 122.

Referring again to FIG. 1 , the AIM system 100 further comprises an AIMapplication (or “app”) 176 that is designed to be executed on a portabledevice 178 such as a smartphone or tablet (but can also be executed onother types of devices such as a desktop or laptop computer).

The AIM app 176 is configured to interact with the AIM system manager162 and the rack controllers 122 (and the intelligent patching equipment104 coupled to the rack controllers 122). The AIM app 176 is configuredso that a user is able to carry out various functions that wouldotherwise be performed using the display unit 136 of each rackcontroller 122. By doing this, the rack controllers 122 can omit thedisplay unit 136, thereby avoiding the cost associated with providingthe display units 136 for the rack controllers 122.

To support configurations of the AIM system 100 where the rackcontrollers 122 are being used without display units 136, the base unit138 of each rack controller 122 in this exemplary embodiment alsocomprises a locate button 180 on the front of the base unit 138. Thislocate button 180 is coupled to the processor 124 in the correspondingrack controller 122 so that the software 126 executing on the processor124 is able to determine when the locate button 180 has been pressed andreleased. In this example, the base unit 138 includes one locate button180 on the front of the base unit 138, but other numbers of locatebuttons 180 can be used in other embodiments (for example, where thereis a separate locate button 180 on the multi-rack rack controller 122for each rack 106 used with that controller 122).

The locate button 180 can be used in various work-flows.

In this example, the rack controller 122 (and the software 126 executingthereon), the AIM system manager 162, and the AIM app 176 are configuredto use the locate button 180 in the following way.

After the rack controller 122 has been installed and configured, when auser is performing a trace or patch at a rack 106 managed by that rackcontroller 122, a user can press the locate button 180 on the front ofthe rack controller 122 to cause the AIM app 176 to shift its focus toshow information for the one or more racks 106 managed by that rackcontroller 122. Thereafter, when local operations are performed at thoseracks 106, the AIM app 176 will show information about the localoperation and the relevant rack controller 122, rack 106, and/orpatching equipment 104. Examples of such local operations includeinserting patch cords into ports 112 of the patching equipment 104 inthe associated racks 106, removing patch cords from ports 112 of thepatching equipment 104 in the associated racks 106, and/or tracing acircuit connection by pressing a port button 118 associated with a port112 of the patching equipment 104 in the associated racks 106.

The rack controller 122 causes the AIM app 176 to shift its focus toshow such information by sending a message to the AIM system manager 162in response to a user pressing the locate button 180. If the rackcontroller 122 where the locate button 180 was pressed is not directlyconnected to the customer LAN 160, the message is forwarded via the RMLAN for the associated zone 158 to the rack controller 122 that isdirectly connected to the customer LAN 160, which forwards the messageto the AIM system manager 162 via the customer LAN 160. In response toreceiving such a message, the AIM system manager 162 sends a message tothe AIM app 176. Each of these messages includes location informationidentifying which rack controller's locate button 180 was pressed. Inresponse to receiving this message, the AIM app 176 shifts its focus toshow information about the rack controller 122 where the locate button180 was pressed, the associated racks 106, and/or the associatedpatching equipment 104.

Without this, it may be difficult or inconvenient for the AIM app 176 todetermine which rack's 106 local information to show. For example, adisplay unit 136 may need to be provided for each rack controller 122 ora user of the AIM app 176 may need to manually enter locationinformation for the relevant rack 106 or rack controller 122 or may needto navigate in the user interface of the AIM app 176 (for example, by“drilling down” a tree-style user-interface element) to the rack 106 orrack controller 122. These approaches can be avoided by configuring therack controller 122 (and the software 126 executing thereon), the AIMsystem manager 162, and the AIM app 176 to use the locate button 180 inas described above.

The locate button 180 can be used in other work-flows. For example, whenthe rack controller 122 is initially installed, the AIM app 176executing on a user's portable device 178 can guide the user through awork flow for setting up and installing and configuring the rackcontroller 122, the patching equipment bus assemblies 146, and theintelligent patching equipment 104. However, when a rack controller 122is first installed, coupled to the customer LAN 160, and powered on,that rack controller 122 may not have been previously discovered by theAIM system manager 162. When multiple rack controllers 122 are beinginstalled at the same time, there is typically a need to provide aninput for the rack controller 122 and/or AIM system manager 162 toidentify or confirm on or for which rack controller 122 a particularoperation in the installation and configuration work-flow is beingperformed.

Where a rack controller 122 has a display unit 136 connected to the baseunit 138, the touch screen 134 of the display unit 136 can be used toprovide such a confirmation input for the rack controller 122 and theAIM system manager 162.

However, where the rack controllers 122 are being used without displayunits 136, it is desirable to be able to provide such a confirmationinput in another way. This can be done using the locate button 180 onthe front of the base unit 138 of each rack controller 122. In this wayother more cumbersome ways of identifying the rack controller 122 (forexample, manually entering a serial number for the rack controller 122into the AIM app 176) need not be used.

FIG. 5 illustrates an exemplary embodiment of an automatedinfrastructure management (AIM) system 500 that is configured to trackconnections that are made using items of patching equipment 104 and 504that implement different types of AIM functionality 110 and 510. Theconnections can be made with various types of cabling, including,without limitation, copper cables and fiber optic cables.

The system 500 is similar to the system 100 of FIG. 1 except asdescribed below. Those elements of the AIM system 500 that are same asthe corresponding elements of AIM system 100 are referenced in FIG. 5using the same reference numerals, and the description of such elementsis not repeated below in connection FIG. 5 .

In the exemplary embodiment shown in FIG. 5 , one set of intelligentpatching equipment 104 implements AIM functionality 110 that requiresthe use of a rack controller 122 that is installed in a rack 106 andthat is coupled to the patching equipment 104 via a patching equipmentbus 123. In the exemplary embodiment shown in FIG. 5 , a second set ofintelligent patching equipment 504 implements AIM functionality 510 thatdoes not require the use of a rack controller installed in a rack 106and instead each item of patching equipment 504 includes a respectiveexternal network interface 564 to couple that item of patching equipment504 directly to the external network 160. In this example, as with theexample shown in FIG. 1 , the external network 160 comprises an ETHERNETLAN and the external network interface 564 comprises an ETHERNETinterface. In this way, each item of patching equipment 504 is able tointeract with the AIM system manager 162 via the customer ETHERNET LAN160.

In the exemplary embodiment shown in FIG. 5 , although the second set ofpatching equipment 504 does not require the use of a rack controller 122in order to function correctly, the rack controller 122 (morespecifically, the software 126 executing on the processor 124 includedin the rack controller 122) and the AIM system manager 162 areconfigured to display information and receive user input for the secondset of patching equipment 504 using the rack controller 122, instead ofor in addition to via the AIM app 176.

Information about the second set of patching equipment 504 iscommunicated between the patching equipment 504 and the system manager162 directly via the customer LAN 162 (that is, without first passingthrough a rack controller 122). Information displayed on the displayunit 136 of the rack controller 122 is communicated from the AIM systemmanager 162 to the rack controller 122. User input received via thedisplay unit 136 of the rack controller 122 is communicated from therack controller 122 to the AIM system manager 162 via the customerETHERNET LAN 162. Any interactions with the second set of patchingequipment 504 that need to be made in response to user input receivedvia the rack controller 122 (for example, if a visual indicator 516 fora given port 512 needs to be illuminated), the AIM system manager 162 isable to perform those interactions directly with the relevant patchingequipment 504. Likewise, information about connection events that a usermakes at the ports 512 of the patching equipment 504 in response toinformation being displayed on the display unit 136 of the rackcontroller 122 are reported to the AIM system manager 162 directly fromthe relevant items of patching equipment 504.

With the AIM system 500, information can be displayed, and user inputcan be received, for a first type of intelligent patching equipment 504using a rack controller 122 that was designed for use with a differenttype of intelligent patching equipment 104. This can be done in additionto or instead of using the AIM app 176. This is done using the AIMsystem manager 162 as the interface instead of using locally installedhardware to provide such an interface, which avoids the cost, space, andpower associated with deploying such local hardware to serve as theinterface.

The methods and techniques described here may be implemented in digitalelectronic circuitry, or with a programmable processor (for example, aspecial-purpose processor or a general-purpose processor such as acomputer) firmware, software, or in combinations of them. Apparatusembodying these techniques may include appropriate input and outputdevices, a programmable processor, and a storage medium tangiblyembodying program instructions for execution by the programmableprocessor. A process embodying these techniques may be performed by aprogrammable processor executing a program of instructions to performdesired functions by operating on input data and generating appropriateoutput. The techniques may advantageously be implemented in one or moreprograms that are executable on a programmable system including at leastone programmable processor coupled to receive data and instructionsfrom, and to transmit data and instructions to, a data storage system,at least one input device, and at least one output device. Generally, aprocessor will receive instructions and data from a read-only memoryand/or a random access memory. Storage devices suitable for tangiblyembodying computer program instructions and data include all forms ofnon-volatile memory, including by way of example semiconductor memorydevices, such as EPROM, EEPROM, and flash memory devices; magnetic diskssuch as internal hard disks and removable disks; magneto-optical disks;and DVD disks. Any of the foregoing may be supplemented by, orincorporated in, specially-designed application-specific integratedcircuits (ASICs).

The foregoing description, including illustrated examples, has beenpresented only for the purpose of illustration and description and isnot intended to be exhaustive or to limit the subject matter to theprecise forms disclosed. Various modifications, adaptations, and usesthereof will be apparent to those skilled in the art without departingfrom this disclosure's scope. The illustrative examples described aboveare given to introduce the reader to the general subject matterdiscussed here and are not intended to limit the scope of the disclosedconcepts.

EXAMPLE EMBODIMENTS

Example 1 includes a multi-rack rack controller for use in an automatedinfrastructure management (AIM) system, the rack controller comprising:a processor configured to execute software; a plurality of independentpatching equipment bus interfaces, each bus interface configured tocouple the processor to a respective patching equipment bus assemblyinstalled in a respective one of multiple racks in which intelligentpatching equipment is installed for communicating with and providingpower to the intelligent patching equipment.

Example 2 includes the rack controller of Example 1, where the processoris configured to determine, for a given item of intelligent patchingequipment that the rack controller is communicating with, which rackthat given item is installed in based on which of the plurality ofpatching equipment bus interfaces is being used to communicate with thatgiven item.

Example 3 includes the rack controller of Example 2, wherein theplurality of patching equipment bus interfaces is arranged to support apredetermined scheme specifying which of the plurality of patchingequipment bus interfaces should be used to couple the intelligentpatching equipment installed in each of the racks to the rackcontroller.

Example 4 includes the rack controller of any of the Examples 1-3,further comprising: an external network interface configured to couplethe processor to an external network.

Example 5 includes the rack controller of Example 4, wherein theexternal network interface comprises an ETHERNET interface configured tocouple the processor to an ETHERNET local area network (LAN).

Example 6 includes the rack controller of any of the Examples 1-5,further comprising: at least one rack controller interface, each rackcontroller interface configured to connect the rack controller toanother rack controller.

Example 7 includes the rack controller of Example 6, wherein each rackcontroller interface comprises a respective termination circuitconfigured to: develop a respective first predetermined level for arespective sense signal of said rack controller interface when said rackcontroller interface is connected to another rack controller; anddevelop a respective second predetermined level for the respective sensesignal of said rack controller interface when said rack controllerinterface is not connected to another rack controller; wherein theprocessor is configured to determine whether each rack controllerinterface is connected to another rack controller as a function of therespective sense signal.

Example 8 includes the rack controller of Example 7, wherein the atleast one rack controller interface comprises first and second rackcontroller interfaces for establishing a network of rack controllers ina daisy chain topology.

Example 9 includes the rack controller of Example 8, wherein therespective first predetermined level of the first rack controllerinterface is not the same as the respective first predetermined level ofthe second rack controller interface.

Example 10 includes the rack controller of any of the Examples 7-9,wherein each rack controller comprises a respective RJ-45 jackconfigured to be connected to a RJ-45 plug attached to an ETHERNETcable.

Example 11 includes the rack controller of any of the Examples 1-10,further comprising a base unit that comprises the processor and theplurality of independent patching equipment bus interfaces.

Example 12 includes the rack controller of Example 11, wherein the baseunit comprises a locate button disposed on the front of the base unit,the locate button coupled to the processor, wherein the locate buttoncan be actuated in order to provide a user input to the processor and tocause the rack controller to send a message operable to cause an appexecuting on a portable device to show information associated with atleast one of the rack controller, one or more of the racks, or thepatching equipment installed in the one or more racks.

Example 13 includes the rack controller of any of the Examples 11-12,further comprising a display unit configured to be connected to the baseunit via a cable.

Example 14 includes a rack controller for use in an automatedinfrastructure management (AIM) system, the rack controller comprising:a processor configured to execute software; at least one patchingequipment bus interface, each patching equipment bus interfaceconfigured to couple the processor to a respective patching equipmentbus assembly installed in a respective rack in which intelligentpatching equipment is installed for communicating with and providingpower to the intelligent patching equipment; and at least one rackcontroller interface, each rack controller interface configured toconnect the rack controller to another rack controller; and wherein eachrack controller interface comprises a respective termination circuitconfigured to: develop a respective first predetermined level for arespective sense signal of said rack controller interface when said rackcontroller interface is connected to another rack controller; anddevelop a respective second predetermined level for the respective sensesignal of said rack controller interface when said rack controllerinterface is not connected to another rack controller; wherein theprocessor is configured to determine whether each rack controllerinterface is connected to another rack controller as a function of therespective sense signal.

Example 15 includes the rack controller of Example 14, wherein the atleast one rack controller interface comprises first and second rackcontroller interfaces for establishing a network of rack controllers ina daisy chain topology.

Example 16 includes the rack controller of Example 15, wherein therespective first predetermined level of the first rack controllerinterface is not the same as the respective first predetermined level ofthe second rack controller interface.

Example 17 includes the rack controller of any of the Examples 14-16,wherein each rack controller comprises a respective RJ-45 jackconfigured to be connected to a RJ-45 plug attached to an ETHERNETcable.

Example 18 includes the rack controller of any of the Examples 14-17,further comprising: an external network interface configured to couplethe processor to an external network.

Example 19 includes the rack controller of Example 18, wherein theexternal network interface comprises an ETHERNET interface configured tocouple the processor to an ETHERNET local area network (LAN).

Example 20 includes the rack controller of any of the Examples 14-19,further comprising a base unit that comprises the processor and thepatching equipment bus interface.

Example 21 includes the rack controller of Example 20, wherein the baseunit comprises a locate button disposed on the front of the base unit,the locate button coupled to the processor, wherein the locate buttoncan be actuated in order to provide a user input to the processor and tocause the rack controller to send a message operable to cause an appexecuting on a portable device to show information associated with atleast one of the rack controller, the rack, or the patching equipmentinstalled in the rack.

Example 22 includes the rack controller of any of the Examples 20-21,further comprising a display unit configured to be connected to the baseunit via a cable.

Example 23 includes the rack controller of any of the Examples 14-22,wherein the at least one bus interface comprises a plurality ofindependent patching equipment bus interfaces, each patching equipmentbus interface configured to couple the processor to a respectivepatching equipment bus assembly installed in a respective one ofmultiple racks in which intelligent patching equipment is installed forcommunicating with and providing power to the intelligent patchingequipment.

Example 24 includes a rack controller for use in an automatedinfrastructure management (AIM) system, the rack controller comprising:a base unit comprising: a processor configured to execute software; atleast one patching equipment bus interface, each patching equipment businterface configured to couple the processor to a respective patchingequipment bus assembly installed in a respective rack in whichintelligent patching equipment is installed for communicating with andproviding power to the intelligent patching equipment; and a locatebutton disposed on the front of the base unit, the locate button coupledto the processor, wherein the locate button can be actuated in order toprovide a user input to the processor even if there is not a displayunit coupled to the base unit and to cause the rack controller to send amessage operable to cause an app executing on a portable device to showinformation associated with at least one of the rack controller, therack, or the patching equipment installed in the rack.

Example 25 includes the rack controller of Example 24, furthercomprising a display unit configured to be connected to the base unitvia a cable.

Example 26 includes the rack controller of any of the Examples 24-25,wherein the at least one bus interface comprises a plurality ofindependent patching equipment bus interfaces, each patching equipmentbus interface configured to couple the processor to a respectivepatching equipment bus assembly installed in a respective one ofmultiple racks in which intelligent patching equipment is installed forcommunicating with and providing power to the intelligent patchingequipment.

Example 27 includes the rack controller of any of the Examples 24-26,further comprising: an external network interface configured to couplethe processor to an external network.

Example 28 includes the rack controller of Example 27, wherein theexternal network interface comprises an ETHERNET interface configured tocouple the processor to an ETHERNET local area network (LAN).

Example 29 includes the rack controller of any of the Examples 24-28,further comprising: at least one rack controller interface, each rackcontroller interface configured to connect the rack controller toanother rack controller.

Example 30 includes the rack controller of Example 29, wherein each rackcontroller interface comprises a respective termination circuitconfigured to: develop a respective first predetermined level for arespective sense signal of said rack controller interface when said rackcontroller interface is connected to another rack controller; anddevelop a respective second predetermined level for the respective sensesignal of said rack controller interface when said rack controllerinterface is not connected to another rack controller; wherein theprocessor is configured to determine whether each rack controllerinterface is connected to another rack controller as a function of therespective sense signal.

Example 31 includes the rack controller of Example 30, wherein the atleast one rack controller interface comprises first and second rackcontroller interfaces for establishing a network of rack controllers ina daisy chain topology.

Example 32 includes the rack controller of Example 31, wherein therespective first predetermined level of the first rack controllerinterface is not the same as the respective first predetermined level ofthe second rack controller interface.

Example 33 includes the rack controller of any of the Examples 29-32,wherein each rack controller comprises a respective RJ-45 jackconfigured to be connected to a RJ-45 plug attached to an ETHERNETcable.

What is claimed is:
 1. A rack controller for use in an automatedinfrastructure management (AIM) system, the rack controller comprising:a processor configured to execute software; a plurality of independentpatching equipment bus interfaces, each bus interface configured topassively couple the processor to a respective patching equipment busassembly installed in a respective one of multiple racks in whichintelligent patching equipment having AIM functionality is installed forcommunicating with and providing power to the intelligent patchingequipment, where the processor is configured to determine, for a givenitem of intelligent patching equipment that the rack controller iscommunicating with, which rack that given item is installed in based onwhich of the plurality of patching equipment bus interfaces is beingused to communicate with that given item; and a base unit that comprisesthe processor and the plurality of independent patching equipment businterfaces, wherein the base unit comprises a locate button disposed onthe front of the base unit, the locate button coupled to the processor,wherein the locate button can be actuated in order to provide a userinput to the processor and to cause the rack controller to send amessage operable to cause an app executing on a portable device to showinformation associated with at least one of the rack controller, one ormore of the racks, or the patching equipment installed in the one ormore racks, wherein the rack controller is located in a rack in themultiple racks and functions as a controller for the multiple racks. 2.The rack controller of claim 1, wherein the plurality of patchingequipment bus interfaces is arranged to support a predetermined schemespecifying which of the plurality of patching equipment bus interfacesshould be used to couple the intelligent patching equipment installed ineach of the racks to the rack controller.
 3. The rack controller ofclaim 1, further comprising: an external network interface configured tocouple the processor to an external network.
 4. The rack controller ofclaim 3, wherein the external network interface comprises an ETHERNETinterface configured to couple the processor to an ETHERNET local areanetwork (LAN).
 5. The rack controller of claim 1, further comprising: atleast one rack controller interface, each rack controller interfaceconfigured to connect the rack controller to another rack controller. 6.The rack controller of claim 5, wherein each rack controller interfacecomprises a respective termination circuit configured to: develop arespective first predetermined level for a respective sense signal ofsaid rack controller interface when said rack controller interface isconnected to another rack controller; and develop a respective secondpredetermined level for the respective sense signal of said rackcontroller interface when said rack controller interface is notconnected to another rack controller; wherein the processor isconfigured to determine whether each rack controller interface isconnected to another rack controller as a function of the respectivesense signal.
 7. The rack controller of claim 6, wherein the at leastone rack controller interface comprises first and second rack controllerinterfaces for establishing a network of rack controllers in a daisychain topology.
 8. The rack controller of claim 7, wherein therespective first predetermined level of the first rack controllerinterface is not the same as the respective first predetermined level ofthe second rack controller interface.
 9. The rack controller of claim 6,wherein each rack controller comprises a respective RJ-45 jackconfigured to be connected to a RJ-45 plug attached to an ETHERNETcable.
 10. The rack controller of claim 1, further comprising a displayunit configured to be connected to the base unit via a cable.
 11. A rackcontroller comprising: a processor configured to execute software; aplurality of patching equipment bus interfaces, each patching equipmentbus interface configured to couple the processor to a respectivepatching equipment bus assembly installed in a respective rack in whichintelligent patching equipment having automated infrastructuremanagement (AIM) functionality is installed for communicating with andproviding power to the intelligent patching equipment, wherein the rackcontroller is located in a rack in multiple racks and functions as acontroller for the multiple racks, where the processor is configured todetermine, for a given item of intelligent patching equipment that therack controller is communicating with, which rack that given item isinstalled in based on which of the plurality of patching equipment businterfaces is being used to communicate with that given item; a baseunit that comprise the processor and the patching equipment businterface, wherein the base unit comprises a locate button disposed onthe front of the base unit, the locate button coupled to the processor,wherein the locate button can be actuated in order to provide a userinput to the processor and to cause the rack controller to send amessage operable to cause an app executing on a portable device to showinformation associated with at least one of the rack controller, therespective rack, or the patching equipment installed in the rack, and atleast two rack controller interfaces, each rack controller interfaceconfigured to connect the rack controller to another rack controller;wherein each rack controller interface comprises a respectivetermination circuit configured to: develop a respective firstpredetermined level for a respective sense signal of said rackcontroller interface when said rack controller interface is connected toanother rack controller; and develop a respective second predeterminedlevel for the respective sense signal of said rack controller interfacewhen said rack controller interface is not connected to another rackcontroller; wherein the processor is configured to determine whethereach rack controller interface is connected to another rack controlleras a function of the respective sense signal.
 12. The rack controller ofclaim 11, wherein the at least two rack controller interfaces comprisesfirst and second rack controller interfaces for establishing a networkof rack controllers in a daisy chain topology.
 13. The rack controllerof claim 12, wherein the respective first predetermined level of thefirst rack controller interface is not the same as the respective firstpredetermined level of the second rack controller interface.
 14. Therack controller of claim 11, wherein each rack controller comprises arespective RJ-45 jack configured to be connected to a RJ-45 plugattached to an ETHERNET cable.
 15. The rack controller of claim 11,further comprising: an external network interface configured to couplethe processor to an external network.
 16. The rack controller of claim15, wherein the external network interface comprises an ETHERNETinterface configured to couple the processor to an ETHERNET local areanetwork (LAN).
 17. The rack controller of claim 6, further comprising adisplay unit configured to be connected to the base unit via a cable.18. A rack controller comprising: a base unit comprising: a processorconfigured to execute software; a plurality of patching equipment businterfaces, each patching equipment bus interface configured to couplethe processor to a respective patching equipment bus assembly installedin a respective rack in which intelligent patching equipment havingautomated infrastructure management (AIM) functionality is installed forcommunicating with and providing power to the intelligent patchingequipment, where the processor is configured to determine, for a givenitem of intelligent patching equipment that the rack controller iscommunicating with, which rack that given item is installed in based onwhich of the plurality of patching equipment bus interfaces is beingused to communicate with that given item; a locate button disposed onthe front of the base unit, the locate button coupled to the processor,wherein the locate button can be actuated to direct the processor tosend messages to a portable device, and wherein the messages sent to theportable device cause the portable device to show information andreceive user input associated with the rack controller and at least oneof the rack and the patching equipment installed in the rack even ifthere is not a display unit coupled to the base unit.
 19. The rackcontroller of claim 18, further comprising a display unit configured tobe connected to the base unit via a cable.
 20. The rack controller ofclaim 18, further comprising: an external network interface configuredto couple the processor to an external network.
 21. The rack controllerof claim 20, wherein the external network interface comprises anETHERNET interface configured to couple the processor to an ETHERNETlocal area network (LAN).
 22. The rack controller of claim 18, furthercomprising: at least one rack controller interface, each rack controllerinterface configured to connect the rack controller to another rackcontroller.
 23. The rack controller of claim 22, wherein each rackcontroller interface comprises a respective termination circuitconfigured to: develop a respective first predetermined level for arespective sense signal of said rack controller interface when said rackcontroller interface is connected to another rack controller; anddevelop a respective second predetermined level for the respective sensesignal of said rack controller interface when said rack controllerinterface is not connected to another rack controller; wherein theprocessor is configured to determine whether each rack controllerinterface is connected to another rack controller as a function of therespective sense signal.
 24. The rack controller of claim 23, whereinthe at least one rack controller interface comprises first and secondrack controller interfaces for establishing a network of rackcontrollers in a daisy chain topology.
 25. The rack controller of claim24, wherein the respective first predetermined level of the first rackcontroller interface is not the same as the respective firstpredetermined level of the second rack controller interface.
 26. Therack controller of claim 22, wherein each rack controller comprises arespective RJ-45 jack configured to be connected to a RJ-45 plugattached to an ETHERNET cable.